Traceability to published standards

I am starting out using DOORS for requirements management for the design of medical devices. A huge number, probably the majority, of our requirements come directly from published standards (IEC 60601 family, AAMI EC13, EC38 etc). I'm struggling to work out the best way of capturing these in DOORS as some of them are very lengthy (hundreds of pages). The only format that I have access to them in, and in fact the only format I can find them in, is PDF.

Not having these in DOORS and traceable seems to make using DOORS at all pointless but the work required to manually enter the complete text of these standards is too large. An option could be to only enter the clause numbers in DOORS and manually look up the text of the clause but that is not ideal either.

Does anyone have any advice on how to handle these? Ideally is anyone using DOORS for the requirements of products with similar standards that would be willing to share their approach?

Thanks in advance.
Stephen
SystemAdmin - Wed Oct 26 17:37:57 EDT 2011

Re: Traceability to published standards
kbmurphy - Wed Oct 26 18:25:44 EDT 2011

This is a major problem but there is no single solution.

The PDF thing is only one hurdle. The bigger hurdle is copyright. Typically these standards cost money. When you purchase the standard, you are doing so only for your individual use as part of the company. You do not have the right to then put the file on the network or on the DOORS server.

So even if you converted the PDF, you still have a copyright issue to worry about. There's a reason these files are only PDFs and are a pain to copy into text.

I tell my clients that the cheaper solution is to just mimic the table of contents in a module, and link to that. Doing this does not make DOORS "pointless" as you say, but it does add the extra step of cross-referencing.

Kevin

Re: Traceability to published standards
Craig_Cordrey - Thu Oct 27 04:04:05 EDT 2011

Does the PDF file have bookmarks? Can those bookmarks be referenced externally (i.e. like a hash-tag in a web-page)? If so, you might be able to use DOORS External links to point to a specific section of the PDF file.

Only a suggestion - I don't know anything about PDF files, so this might not be possible. You could at least use the External link to point to the right document on your network.

Re: Traceability to published standards
OurGuest - Thu Oct 27 04:16:47 EDT 2011

Craig_Cordrey - Thu Oct 27 04:04:05 EDT 2011
Does the PDF file have bookmarks? Can those bookmarks be referenced externally (i.e. like a hash-tag in a web-page)? If so, you might be able to use DOORS External links to point to a specific section of the PDF file.

Only a suggestion - I don't know anything about PDF files, so this might not be possible. You could at least use the External link to point to the right document on your network.

Assuming you have the legal right, one easy solution is as follows:

Convert each page of PDF to a JPEG, then import the JPEGs into DOORS module. Then your specs can link to the appropriate page.

NOTE: Adobe Acrobat will save each page to JPEG and identifies each page in a numeric sequence. You can then either import JPEGs into DOORS using DXL or you can import into MSWord prior to exporting to DOORS.

Re: Traceability to published standards
OurGuest - Thu Oct 27 04:25:57 EDT 2011

OurGuest - Thu Oct 27 04:16:47 EDT 2011
Assuming you have the legal right, one easy solution is as follows:

Convert each page of PDF to a JPEG, then import the JPEGs into DOORS module. Then your specs can link to the appropriate page.

NOTE: Adobe Acrobat will save each page to JPEG and identifies each page in a numeric sequence. You can then either import JPEGs into DOORS using DXL or you can import into MSWord prior to exporting to DOORS.

Another approach is to create a text attribute in you DOORS module then enter appropriate info into this attribute to indicate to the reader where to go to see reference information.

NOTE: DXL can read the textual information and actually load the PDF and go to the appropriate page/paragraph/bookmark. However, each user would have to have Adobe Acrobat installed for this solution. (Probably, no third party PDF reader has this capability.)

Re: Traceability to published standards
Ron_Lewis - Fri Oct 28 01:00:45 EDT 2011

OurGuest - Thu Oct 27 04:16:47 EDT 2011
Assuming you have the legal right, one easy solution is as follows:

Convert each page of PDF to a JPEG, then import the JPEGs into DOORS module. Then your specs can link to the appropriate page.

NOTE: Adobe Acrobat will save each page to JPEG and identifies each page in a numeric sequence. You can then either import JPEGs into DOORS using DXL or you can import into MSWord prior to exporting to DOORS.

Another approach is to convert the PDF to images and put all relevant images into a shared directory. Then connect requirements by external links to the relevent images. Converting PDF to images can be done with multiple different tools and if all else fails, you can use screen capture.

Re: Traceability to published standards
OurGuest - Fri Oct 28 08:07:11 EDT 2011

Ron_Lewis - Fri Oct 28 01:00:45 EDT 2011
Another approach is to convert the PDF to images and put all relevant images into a shared directory. Then connect requirements by external links to the relevent images. Converting PDF to images can be done with multiple different tools and if all else fails, you can use screen capture.

In some countries there is a fair use law
that may permit the use of copyrighted
material for the purposes as outlined in
this thread of discussion.

In the United States a court ruling was
decided based on the following:


We must often... look to the nature and objects of the selections made, the quantity and value of the materials used, and the degree in which the use may prejudice the sale, or diminish the profits, or supersede the objects, of the original work.


The use of copyrighted work for
linking to show context of a
requirement probably will not
prejudice the sale, or diminish
the profits, or supersede the
objects, of the original work.

Is there any other opinions on this?

Re: Traceability to published standards
kbmurphy - Fri Oct 28 13:42:45 EDT 2011

OurGuest - Fri Oct 28 08:07:11 EDT 2011
In some countries there is a fair use law
that may permit the use of copyrighted
material for the purposes as outlined in
this thread of discussion.

In the United States a court ruling was
decided based on the following:


We must often... look to the nature and objects of the selections made, the quantity and value of the materials used, and the degree in which the use may prejudice the sale, or diminish the profits, or supersede the objects, of the original work.


The use of copyrighted work for
linking to show context of a
requirement probably will not
prejudice the sale, or diminish
the profits, or supersede the
objects, of the original work.

Is there any other opinions on this?

Yes. The only acceptable opinion: Consult your company's lawyer before putting any copyrighted standards documents into your DOORS server.

Re: Traceability to published standards
llandale - Fri Oct 28 15:56:18 EDT 2011

kbmurphy - Fri Oct 28 13:42:45 EDT 2011
Yes. The only acceptable opinion: Consult your company's lawyer before putting any copyrighted standards documents into your DOORS server.

Out of curiosity, do you know of a specific company that has been fined or otherwise punished for this?

Re: Traceability to published standards
SystemAdmin - Mon Oct 31 07:49:34 EDT 2011

kbmurphy - Wed Oct 26 18:25:44 EDT 2011
This is a major problem but there is no single solution.

The PDF thing is only one hurdle. The bigger hurdle is copyright. Typically these standards cost money. When you purchase the standard, you are doing so only for your individual use as part of the company. You do not have the right to then put the file on the network or on the DOORS server.

So even if you converted the PDF, you still have a copyright issue to worry about. There's a reason these files are only PDFs and are a pain to copy into text.

I tell my clients that the cheaper solution is to just mimic the table of contents in a module, and link to that. Doing this does not make DOORS "pointless" as you say, but it does add the extra step of cross-referencing.

Kevin

Thanks for your reply.

I hadn't fully considered the licensing aspects. It looks as though our license subscription allows anyone in the company to download/view and print as many copies as they want, but I think it does preclude storing it "locally" on a network.

If there was a legal source of these standards in a format that could be used within DOORS then we possibly could make a case to purchase/license them but I assume no one is aware of such an offering.

It looks like the table of contents approach is a reasonable compromise. I didn't mean that I thought this made DOORS pointless, I was meaning that if we didn't include these standards at all then for our application it would be more or less pointless as they are such a large proportion of the requirements.

Stephen

Re: Traceability to published standards
SystemAdmin - Mon Oct 31 08:48:09 EDT 2011

Craig_Cordrey - Thu Oct 27 04:04:05 EDT 2011
Does the PDF file have bookmarks? Can those bookmarks be referenced externally (i.e. like a hash-tag in a web-page)? If so, you might be able to use DOORS External links to point to a specific section of the PDF file.

Only a suggestion - I don't know anything about PDF files, so this might not be possible. You could at least use the External link to point to the right document on your network.

PDF files can have bookmarks which you can use when creating external links. However, I experimented with this a loooong time ago, and found a nasty drawback. If you follow the link, the PDF will open at the page where the bookmark is, however, it will not highlight the bookmark as with MS Word... So if three is lots of text on the page it will still be hard to find the exact location...

And then there is the license/copyright issue to solve.

One solution that I've used is to create a list of references (ยง, chapter, req no, verision, issue...)for the applicable requirements in a DOORS module and use DOORS links to that list. For the specific details or text you would then have to go to your copy of the standard...

Re: Traceability to published standards
SystemAdmin - Mon Oct 31 11:08:41 EDT 2011

I think most companies will have this dilemma. Some will have it more than others. At first I tried putting in external links but that was a nuisance. Finally we chose to solve it like a database foreign table. A "Foreign Verifications Links" module is sandwiched between the module that needs to make a reference and the non-DOORS reference document.

If the non-DOORS reference document is available on-line , you can put a hyperlink in the "Foreign Verifications Links" module.

If you have a lot of this, you can make a heading with the name of the foreign document. Just beneath the heading you could put in the details like revision, author, version, where it is.

If you just want to point to the document you can stop here.

Alternatively, you could have chapters, pages, paragraph numbers (or whatever) as rows that are children of the foreign document. You may optionally put text here too if you want to take it this far.

Your DOORS module would have out-links to rows in the foreign module. This way access is quick and has the appearance of a normal link.

If a user follows a link, they will get as far as the "Foreign Verifications Links" module. From there they would have to follow an HTTP: hyperlink to get to the source or open to a page in a book on their desk.

I attached an illustration.
Attachments

attachment_14698878_ForeignLinkModule.png